Missed Telephone Call Management for a Portable Multifunction Device

ABSTRACT

In one aspect of the invention, a computer-implemented method is disclosed for use in conjunction with a portable electronic device with a touch screen display. A list of items comprising missed telephone calls is displayed. Upon detecting user selection of an item in the list, contact information is displayed for a respective caller corresponding to the user selected item. The displayed contact information includes a plurality of contact objects that include a first contact object, comprising a telephone number object having a first telephone number associated with the missed telephone call, and a second contact object. Upon detecting user selection of the second contact object, a communication with the respective caller is initiated via a modality corresponding to the second contact object.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/418,322, filed Mar. 12, 2012, now U.S. Pat. No. 8,255,003, which is acontinuation of U.S. patent application Ser. No. 13/205,586, filed Aug.8, 2011, entitled “Missed Telephone Call Management for a PortableMultifunction Device,” now U.S. Pat. No. 8,135,387, which is adivisional application of U.S. patent application Ser. No. 11/769,694,filed Jun. 27, 2007, entitled “Missed Telephone Call Management for aPortable Multifunction Device,” now U.S. Pat. No. 8,014,760, whichclaims priority to: (A) U.S. Provisional Patent Application No.60/879,469, filed Jan. 8, 2007, entitled “Portable MultifunctionDevice”; (B) U.S. Provisional Patent Application No. 60/879,253, filedJan. 7, 2007, entitled “Portable Multifunction Device”; (C) U.S.Provisional Patent Application No. 60/883,782, filed Jan. 6, 2007,entitled “Telephone Call Management for a Portable MultifunctionDevice”; and (D) U.S. Provisional Patent Application No. 60/824,769,filed Sep. 6, 2006, entitled “Portable Multifunction Device.” All ofthese applications are incorporated by referenced herein in theirentirety.

This application is related to the following applications: (1) U.S.patent application Ser. No. 10/188,182, “Touch Pad For Handheld Device,”filed on Jul. 1, 2002; (2) U.S. patent application Ser. No. 10/722,948,“Touch Pad For Handheld Device,” filed on Nov. 25, 2003; (3) U.S. patentapplication Ser. No. 10/643,256, “Movable Touch Pad With AddedFunctionality,” filed on Aug. 18, 2003; (4) U.S. patent application Ser.No. 10/654,108, “Ambidextrous Mouse,” filed on Sep. 2, 2003; (5) U.S.patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filedon May 6, 2004; (6) U.S. patent application Ser. No. 10/903,964,“Gestures For Touch Sensitive Input Devices,” filed on Jul. 30, 2004;(7) U.S. patent application Ser. No. 11/038,590, “Mode-Based GraphicalUser Interfaces For Touch Sensitive Input Devices” filed on Jan. 18,2005; (8) U.S. patent application Ser. No. 11/057,050, “DisplayActuator,” filed on Feb. 11, 2005; (9) U.S. Provisional PatentApplication No. 60/658,777, “Multi-Functional Hand-Held Device,” filedMar. 4, 2005; and (10) U.S. patent application Ser. No. 11/367,749,“Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of theseapplications are incorporated by reference herein.

TECHNICAL FIELD

The disclosed embodiments relate generally to portable electronicdevices, and more particularly, to portable devices that are capable ofperforming multiple communication functions including telephony.

BACKGROUND

As portable electronic devices become more compact, and the number offunctions performed by a given device increase, it has become asignificant challenge to design a user interface that allows users toeasily interact with a multifunction device. This challenge isparticular significant for handheld portable devices, which have muchsmaller screens than desktop or laptop computers. This situation isunfortunate because the user interface is the gateway through whichusers receive not only content but also responses to user actions orbehaviors, including user attempts to access a device's features, tools,and functions. Some portable communication devices (e.g., mobiletelephones, sometimes called mobile phones, cell phones, cellulartelephones, and the like) have resorted to adding more pushbuttons,increasing the density of push buttons, overloading the functions ofpushbuttons, or using complex menu systems to allow a user to access,store and manipulate data. These conventional user interfaces oftenresult in complicated key sequences and menu hierarchies that must bememorized by the user.

Many conventional user interfaces, such as those that include physicalpushbuttons, are also inflexible. This is unfortunate because it mayprevent a user interface from being configured and/or adapted by eitheran application running on the portable device or by users. When coupledwith the time consuming requirement to memorize multiple key sequencesand menu hierarchies, and the difficulty in activating a desiredpushbutton, such inflexibility is frustrating to most users.

In particular, user interfaces for managing missed telephone calls andprior telephone calls may be frustrating to users. Multiple keysequences and complex menu hierarchies may prevent a user from beingable to respond to a missed call easily or to access information aboutprior calls easily.

Accordingly, there is a need for portable multifunction devices withmore transparent and intuitive user interfaces for managing missedtelephone calls and prior telephone calls that are easy to use,configure, and/or adapt.

SUMMARY

The above deficiencies and other problems associated with userinterfaces for portable devices are reduced or eliminated by thedisclosed portable multifunction device. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen”) with agraphical user interface (GUI), one or more processors, memory and oneor more modules, programs or sets of instructions stored in the memoryfor performing multiple functions. In some embodiments, the userinteracts with the GUI primarily through finger contacts and gestures onthe touch-sensitive display. In some embodiments, the functions mayinclude telephoning, video conferencing, e-mailing, instant messaging,blogging, digital photographing, digital videoing, web browsing, digitalmusic playing, and/or digital video playing. Instructions for performingthese functions may be included in a computer program product configuredfor execution by one or more processors.

A computer-implemented method is disclosed for use in conjunction with aportable electronic device with a touch screen display. A list of itemscomprising missed telephone calls is displayed. Upon detecting userselection of an item in the list, contact information is displayed for arespective caller corresponding to the user selected item. The displayedcontact information includes a plurality of contact objects that includea first contact object, comprising a telephone number object having afirst telephone number associated with the missed telephone call, and asecond contact object. Upon detecting user selection of the secondcontact object, a communication with the respective caller is initiatedvia a modality corresponding to the second contact object.

A computer-implemented method is disclosed for use in conjunction with aportable electronic device with a touch screen display. A list of itemscomprising missed telephone calls is displayed. Upon detecting fingercontact with a first portion of a user selected item in the list, areturn telephone call is initiated to a return telephone numberassociated with the user selected item. Upon detecting finger contactwith a second portion of the respective item in the list, contactinformation is displayed for a respective caller associated with theuser selected item. The displayed contact information includes aplurality of contact objects that include a first contact object,comprising a telephone number object having the return telephone number,and a second contact object. Upon detecting user selection of the secondcontact object, a communication is initiated with the respective callervia a modality corresponding to the second contact object.

A computer-implemented method is disclosed for use in conjunction with aportable electronic device with a touch screen display. Missed telephonecall information is displayed, including a list of items, wherein atleast one of the items corresponds to a plurality of missed telephonecalls from a respective caller.

A computer-implemented method is disclosed for use in conjunction with aportable electronic device with a touch screen display with a pluralityof user interface objects. Telephone call information is displayed,including a list of items, wherein at least one of the items correspondsto a plurality of telephone calls with a respective caller. A scrollinggesture is detected comprising substantially vertical movement of a usercontact with the touch screen display. In response to the scrollinggesture, the display of telephone call information is scrolled.

A computer-implemented method is disclosed for use in conjunction with aportable electronic device with a touch screen display with a pluralityof user interface objects. A list of items for prior telephone calls isdisplayed. Upon detecting finger contact with a first portion of a userselected item in the list, a telephone call is initiated to a primarytelephone number associated with the user selected item. Upon detectingfinger contact with a second portion of the respective item in the list,contact information is displayed for a respective caller associated withthe user selected item. The displayed contact information includes aplurality of contact objects that include a first contact object,comprising a telephone number object having the primary telephonenumber, and a second contact object. Upon detecting user selection ofthe second contact object, a communication is initiated with therespective caller via a modality corresponding to the second contactobject.

A computer program product for use in conjunction with a portableelectronic device with a touch screen display with a plurality of userinterface objects is disclosed. The computer program product comprises acomputer readable storage medium and a computer program mechanismembedded therein. The computer program mechanism comprises instructionsfor displaying a list of items for missed telephone calls. The computerprogram mechanism also comprises instructions for displaying, upondetecting user selection of an item in the list, contact information fora respective caller corresponding to the user selected item. Thedisplayed contact information includes a plurality of contact objectsthat include a first contact object, comprising a telephone numberobject having a first telephone number associated with the missedtelephone call, and a second contact object. The computer programmechanism further comprises instructions for initiating, upon detectinguser selection of the second contact object, a communication with therespective caller via a modality corresponding to the second contactobject.

A computer program product for use in conjunction with a portableelectronic device with a touch screen display with a plurality of userinterface objects is disclosed. The computer program product comprises acomputer readable storage medium and a computer program mechanismembedded therein. The computer program mechanism comprises instructionsfor displaying a list of items for missed telephone calls andinstructions for initiating, upon detecting finger contact with a firstportion of a user selected item in the list, a return telephone call toa return telephone number associated with the user selected item. Thecomputer program mechanism also comprises instructions for displaying,upon detecting finger contact with a second portion of the respectiveitem in the list, contact information for a respective caller associatedwith the user selected item. The displayed contact information includesa plurality of contact objects that include a first contact object,comprising a telephone number object having the return telephone number,and a second contact object. The computer program mechanism furthercomprises instructions for initiating, upon detecting user selection ofthe second contact object, a communication with the respective callervia a modality corresponding to the second contact object.

A computer program product for use in conjunction with a portableelectronic device with a touch screen display with a plurality of userinterface objects is disclosed. The computer program product comprises acomputer readable storage medium and a computer program mechanismembedded therein. The computer program mechanism comprises instructionsfor displaying missed telephone call information, including a list ofitems, wherein at least one of the items corresponds to a plurality ofmissed telephone calls from a respective caller.

A computer program product for use in conjunction with a portableelectronic device with a touch screen display with a plurality of userinterface objects is disclosed. The computer program product comprises acomputer readable storage medium and a computer program mechanismembedded therein. The computer program mechanism comprises instructionsfor displaying telephone call information, including a list of items,wherein at least one of the items corresponds to a plurality oftelephone calls with a respective caller. The computer program mechanismalso comprises instructions for detecting a scrolling gesture comprisingsubstantially vertical movement of user contact with the touch screendisplay and instructions for responding to the scrolling gesture byscrolling the display of telephone call information.

A computer program product for use in conjunction with a portableelectronic device with a touch screen display with a plurality of userinterface objects is disclosed. The computer program product comprises acomputer readable storage medium and a computer program mechanismembedded therein. The computer program mechanism comprises instructionsfor displaying a list of items for prior telephone calls andinstructions for initiating, upon detecting finger contact with a firstportion of a user selected item in the list, a telephone call to aprimary telephone number associated with the user selected item. Thecomputer program mechanism also comprises instructions for displaying,upon detecting finger contact with a second portion of the respectiveitem in the list, contact information for a respective caller associatedwith the user selected item. The displayed contact information includesa plurality of contact objects that include a first contact object,comprising a telephone number object having the primary telephonenumber, and a second contact object. The computer program mechanismfurther comprises instructions for initiating, upon detecting userselection of the second contact object, a communication with therespective caller via a modality corresponding to the second contactobject.

A portable electronic device with a touch screen display with aplurality of user interface objects is disclosed, comprising memory, oneor more processors, and one or more programs stored in the memory andconfigured for execution by the one or more processors. The one or moreprograms include instructions for displaying a list of items for missedtelephone calls and instructions for displaying, upon detecting userselection of an item in the list, contact information for a respectivecaller corresponding to the user selected item. The displayed contactinformation includes a plurality of contact objects that include a firstcontact object, comprising a telephone number object having a firsttelephone number associated with the missed telephone call, and a secondcontact object. The one or more programs also include instructions forinitiating, upon detecting user selection of the second contact object,a communication with the respective caller via a modality correspondingto the second contact object.

A portable electronic device with a touch screen display with aplurality of user interface objects is disclosed, comprising memory, oneor more processors, and one or more programs stored in the memory andconfigured for execution by the one or more processors. The one or moreprograms include instructions for displaying a list of items for missedtelephone calls and instructions for initiating, upon detecting fingercontact with a first portion of a user selected item in the list, areturn telephone call to a return telephone number associated with theuser selected item. The one or more programs also include instructionsfor displaying, upon detecting finger contact with a second portion ofthe respective item in the list, contact information for a respectivecaller associated with the user selected item. The displayed contactinformation includes a plurality of contact objects that include a firstcontact object, comprising a telephone number object having the returntelephone number, and a second contact object. The one or more programsfurther include instructions for initiating, upon detecting userselection of the second contact object, a communication with therespective caller via a modality corresponding to the second contactobject.

A portable electronic device with a touch screen display with aplurality of user interface objects is disclosed, comprising memory, oneor more processors, and one or more programs stored in the memory andconfigured for execution by the one or more processors. The one or moreprograms include instructions for displaying missed telephone callinformation, including a list of items, wherein at least one of theitems corresponds to a plurality of missed telephone calls from arespective caller.

A portable electronic device with a touch screen display with aplurality of user interface objects is disclosed, comprising memory, oneor more processors, and one or more programs stored in the memory andconfigured for execution by the one or more processors. The one or moreprograms include instructions for displaying telephone call information,including a list of items, wherein at least one of the items correspondsto a plurality of telephone calls with a respective caller. The one ormore programs also include instructions for detecting a scrollinggesture comprising substantially vertical movement of user contact withthe touch screen display and instructions for responding to thescrolling gesture by scrolling the display of telephone callinformation.

A portable electronic device with a touch screen display with aplurality of user interface objects is disclosed, comprising memory, oneor more processors, and one or more programs stored in the memory andconfigured for execution by the one or more processors. The one or moreprograms include instructions for displaying a list of items for priortelephone calls and instructions for initiating, upon detecting fingercontact with a first portion of a user selected item in the list, atelephone call to a primary telephone number associated with the userselected item. The one or more programs also include instructions fordisplaying, upon detecting finger contact with a second portion of therespective item in the list, contact information for a respective callerassociated with the user selected item. The displayed contactinformation includes a plurality of contact objects that include a firstcontact object, comprising a telephone number object having the primarytelephone number, and a second contact object. The one or more programsfurther include instructions for initiating, upon detecting userselection of the second contact object, a communication with therespective caller via a modality corresponding to the second contactobject.

The disclosed embodiments provide more transparent and intuitive userinterfaces for managing missed telephone calls and prior telephonecalls, thereby reducing user frustrations.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of theinvention as well as additional embodiments thereof, reference should bemade to the Description of Embodiments below, in conjunction with thefollowing drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIG. 1 is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 illustrates an exemplary user interface for unlocking a portableelectronic device in accordance with some embodiments.

FIG. 4 illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 5 illustrates an exemplary user interface for listing instantmessage conversations on a portable multifunction device in accordancewith some embodiments.

FIGS. 6A-6E illustrate an exemplary user interface for inputting textfor an instant message in accordance with some embodiments.

FIG. 7 illustrates an exemplary user interface for deleting an instantmessage conversation in accordance with some embodiments.

FIGS. 8A and 8B illustrate an exemplary user interface for a contactlist in accordance with some embodiments.

FIG. 9 illustrates an exemplary user interface for entering a phonenumber for instant messaging in accordance with some embodiments.

FIGS. 10A-10M illustrate an exemplary user interface for displaying andmanaging contacts in accordance with some embodiments.

FIGS. 11A-11C illustrate an exemplary user interface for displaying andmanaging favorite contacts in accordance with some embodiments.

FIGS. 12A-12D illustrate an exemplary user interface for displaying andmanaging recent calls in accordance with some embodiments.

FIG. 13 illustrates an exemplary dial pad interface for calling inaccordance with some embodiments.

FIGS. 14A-14D illustrate exemplary user interfaces displayed during acall in accordance with some embodiments.

FIGS. 15A and 15B illustrate an exemplary user interface displayedduring an incoming call in accordance with some embodiments.

FIGS. 16A and 16B illustrate an exemplary user interface for voicemailin accordance with some embodiments.

FIG. 17 illustrates an exemplary user interface for organizing andmanaging email in accordance with some embodiments.

FIGS. 18A and 18B illustrate an exemplary user interface for creatingemails in accordance with some embodiments.

FIGS. 19A-19F illustrate an exemplary user interface for displaying andmanaging an inbox in accordance with some embodiments.

FIG. 20 illustrates an exemplary user interface for setting email userpreferences in accordance with some embodiments.

FIGS. 21A and 21B illustrate an exemplary user interface for creatingand managing email rules in accordance with some embodiments.

FIGS. 22A and 22B illustrate an exemplary user interface for movingemail messages in accordance with some embodiments.

FIG. 23 is a flow diagram illustrating a process for handling missedtelephone calls at a portable electronic device with a touch screendisplay in accordance with some embodiments.

FIG. 24 is a flow diagram illustrating a process for handling missedtelephone calls at a portable electronic device with a touch screendisplay in accordance with some embodiments.

FIG. 25 is a flow diagram illustrating a process for handling missedtelephone calls at a portable electronic device with a touch screendisplay in accordance with some embodiments.

FIG. 26 is a flow diagram illustrating a process for handling priortelephone call information at a portable electronic device with a touchscreen display with a plurality of user interface objects in accordancewith some embodiments.

FIG. 27 is a flow diagram illustrating a process for handling priortelephone calls at a portable electronic device with a touch screendisplay with a plurality of user interface objects in accordance withsome embodiments.

FIG. 28 is a flow diagram illustrating a process for handling incomingtelephone calls at a portable electronic device with a touch screendisplay with a plurality of user interface objects in accordance withsome embodiments.

FIG. 29 is a flow diagram illustrating a process for handlingestablished telephone calls at a portable electronic device with a touchscreen display with a plurality of user interface objects in accordancewith some embodiments.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one of ordinary skill in the art that the present inventionmay be practiced without these specific details. In other instances,well-known methods, procedures, components, circuits, and networks havenot been described in detail so as not to unnecessarily obscure aspectsof the embodiments.

Embodiments of a portable multifunction device, user interfaces for suchdevices, and associated processes for using such devices are described.In some embodiments, the device is a portable communications device suchas a mobile telephone that also contains other functions, such as PDAand/or music player functions.

The user interface may include a click wheel in addition to a touchscreen. A click wheel is a physical user-interface device that mayprovide navigation commands based on an angular displacement of thewheel or a point of contact with the wheel by a user of the device. Aclick wheel may also be used to provide a user command corresponding toselection of one or more items, for example, when the user of the devicepresses down on at least a portion of the wheel or the center of thewheel. For simplicity, in the discussion that follows, a portablemultifunction device that includes a touch screen is used as anexemplary embodiment. It should be understood, however, that some of theuser interfaces and associated processes may be applied to otherdevices, such as personal computers and laptop computers, that mayinclude one or more other physical user-interface devices, such as aclick wheel, a physical keyboard, a mouse and/or a joystick.

The device supports a variety of applications, such as a telephoneapplication, a video conferencing application, an e-mail application, aninstant messaging application, a blogging application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as the touchscreen. One or more functions of the touch screen as well ascorresponding information displayed on the device may be adjusted and/orvaried from one application to the next and/or within a respectiveapplication. In this way, a common physical architecture (such as thetouch screen) of the device may support the variety of applications withuser interfaces that are intuitive and transparent.

The user interfaces may include one or more soft keyboard embodiments.The soft keyboard embodiments may include standard (QWERTY) and/ornon-standard configurations of symbols on the displayed icons of thekeyboard, such as those described in U.S. patent application Ser. Nos.11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24,2006, and 11/459,615, “Touch Screen Keyboards For Portable ElectronicDevices,” filed Jul. 24, 2006, the contents of which are herebyincorporated by reference. The keyboard embodiments may include areduced number of icons (or soft keys) relative to the number of keys inexisting physical keyboards, such as that for a typewriter. This maymake it easier for users to select one or more icons in the keyboard,and thus, one or more corresponding symbols. The keyboard embodimentsmay be adaptive. For example, displayed icons may be modified inaccordance with user actions, such as selecting one or more icons and/orone or more corresponding symbols. One or more applications on theportable device may utilize common and/or different keyboardembodiments. Thus, the keyboard embodiment used may be tailored to atleast some of the applications. In some embodiments, one or morekeyboard embodiments may be tailored to a respective user. For example,based on a word usage history (lexicography, slang, individual usage) ofthe respective user. Some of the keyboard embodiments may be adjusted toreduce a probability of a user error when selecting one or more icons,and thus one or more symbols, when using the soft keyboard embodiments.

Attention is now directed towards embodiments of the device. FIG. 1 is ablock diagram illustrating a portable multifunction device 100 with atouch-sensitive display 112 in accordance with some embodiments. Thetouch-sensitive display 112 is sometimes called a “touch screen” forconvenience, and may also be known as or called a touch-sensitivedisplay system. The device 100 may include a memory 102 (which mayinclude one or more computer readable storage mediums), a memorycontroller 122, one or more processing units (CPU's) 120, a peripheralsinterface 118, RF circuitry 108, audio circuitry 110, a speaker 111, amicrophone 113, an input/output (I/O) subsystem 106, other input orcontrol devices 116, and an external port 124. The device 100 mayinclude one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that the device 100 is only one example of aportable multifunction device 100, and that the device 100 may have moreor fewer components than shown, may combine two or more components, or amay have a different configuration or arrangement of the components. Thevarious components shown in FIG. 1 may be implemented in hardware,software or a combination of both hardware and software, including oneor more signal processing and/or application specific integratedcircuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of the device 100,such as the CPU 120 and the peripherals interface 118, may be controlledby the memory controller 122.

The peripherals interface 118 couples the input and output peripheralsof the device to the CPU 120 and memory 102. The one or more processors120 run or execute various software programs and/or sets of instructionsstored in memory 102 to perform various functions for the device 100 andto process data.

In some embodiments, the peripherals interface 118, the CPU 120, and thememory controller 122 may be implemented on a single chip, such as achip 104. In some other embodiments, they may be implemented on separatechips.

The RF (radio frequency) circuitry 108 receives and sends RF signals,also called electromagnetic signals. The RF circuitry 108 convertselectrical signals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. The RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. The RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of a plurality of communications standards, protocols andtechnologies, including but not limited to Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), high-speeddownlink packet access (HSDPA), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for email, instant messaging, and/orShort Message Service (SMS)), or any other suitable communicationprotocol, including communication protocols not yet developed as of thefiling date of this document.

The audio circuitry 110, the speaker 111, and the microphone 113 providean audio interface between a user and the device 100. The audiocircuitry 110 receives audio data from the peripherals interface 118,converts the audio data to an electrical signal, and transmits theelectrical signal to the speaker 111. The speaker 111 converts theelectrical signal to human-audible sound waves. The audio circuitry 110also receives electrical signals converted by the microphone 113 fromsound waves. The audio circuitry 110 converts the electrical signal toaudio data and transmits the audio data to the peripherals interface 118for processing. Audio data may be retrieved from and/or transmitted tomemory 102 and/or the RF circuitry 108 by the peripherals interface 118.In some embodiments, the audio circuitry 110 also includes a headsetjack (not shown). The headset jack provides an interface between theaudio circuitry 110 and removable audio input/output peripherals, suchas output-only headphones or a headset with both output (e.g., aheadphone for one or both ears) and input (e.g., a microphone).

The I/O subsystem 106 couples input/output peripherals on the device100, such as the touch screen 112 and other input/control devices 116,to the peripherals interface 118. The I/O subsystem 106 may include adisplay controller 156 and one or more input controllers 160 for otherinput or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input/control devices 116 may include physical buttons(e.g., push buttons, rocker buttons, etc.), dials, slider switches,joysticks, click wheels, and so forth. In some alternate embodiments,input controller(s) 160 may be coupled to any (or none) of thefollowing: a keyboard, infrared port, USB port, and a pointer devicesuch as a mouse. The one or more buttons (e.g., 208, FIG. 2) may includean up/down button for volume control of the speaker 111 and/or themicrophone 113. The one or more buttons may include a push button (e.g.,206, FIG. 2). A quick press of the push button may disengage a lock ofthe touch screen 112 or begin a process that uses gestures on the touchscreen to unlock the device, as described in U.S. patent applicationSer. No. 11/322,549 (Unlocking a Device by Performing Gestures on anUnlock Image, filed Dec. 23, 2005), which is hereby incorporated byreference. A longer press of the push button (e.g., 206) may turn powerto the device 100 on or off. The user may be able to customize afunctionality of one or more of the buttons. The touch screen 112 isused to implement virtual or soft buttons and one or more softkeyboards.

The touch-sensitive touch screen 112 provides an input interface and anoutput interface between the device and a user. The display controller156 receives and/or sends electrical signals from/to the touch screen112. The touch screen 112 displays visual output to the user. The visualoutput may include graphics, text, icons, video, and any combinationthereof (collectively termed “graphics”). In some embodiments, some orall of the visual output may correspond to user-interface objects,further details of which are described below.

A touch screen 112 has a touch-sensitive surface, sensor or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. The touch screen 112 and the display controller 156 (along withany associated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on the touchscreen 112 and converts the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages orimages) that are displayed on the touch screen. In an exemplaryembodiment, a point of contact between a touch screen 112 and the usercorresponds to a finger of the user.

The touch screen 112 may use LCD (liquid crystal display) technology, orLPD (light emitting polymer display) technology, although other displaytechnologies may be used in other embodiments. The touch screen 112 andthe display controller 156 may detect contact and any movement orbreaking thereof using any of a plurality of touch sensing technologiesnow known or later developed, including but not limited to capacitive,resistive, infrared, and surface acoustic wave technologies, as well asother proximity sensor arrays or other elements for determining one ormore points of contact with a touch screen 112. A touch-sensitivedisplay in some embodiments of the touch screen 112 may be analogous tothe multi-touch sensitive tablets described in the following U.S. Pat.Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1,each of which is hereby incorporated by reference. However, a touchscreen 112 displays visual output from the portable device 100, whereastouch sensitive tablets do not provide visual output. The touch screen112 may have a resolution in excess of 100 dpi. In an exemplaryembodiment, the touch screen has a resolution of approximately 168 dpi.The user may make contact with the touch screen 112 using any suitableobject or appendage, such as a stylus, a finger, and so forth. In someembodiments, the user interface is designed to work primarily withfinger-based contacts and gestures, which are much less precise thanstylus-based input due to the larger area of contact of a finger on thetouch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

A touch-sensitive display in some embodiments of the touch screen 112may be as described in the following applications: (1) U.S. patentapplication Ser. No. 11/381,313, “Multipoint Touch Surface Controller,”filed on May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862,“Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patentapplication Ser. No. 10/903,964, “Gestures For Touch Sensitive InputDevices,” filed on Jul. 30, 2004; (4) U.S. patent application Ser. No.11/048,264, “Gestures For Touch Sensitive Input Devices,” filed on Jan.31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-BasedGraphical User Interfaces For Touch Sensitive Input Devices,” filed onJan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “VirtualInput Device Placement On A Touch Screen User Interface,” filed on Sep.16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation OfA Computer With A Touch Screen Interface,” filed on Sep. 16, 2005; (8)U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys OfA Touch-Screen Virtual Keyboard,” filed on Sep. 16, 2005; and (9) U.S.patent application Ser. No. 11/367,749, “Multi-Functional Hand-HeldDevice,” filed on Mar. 3, 2006. All of these applications areincorporated by reference herein.

In some embodiments, in addition to the touch screen, the device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom the touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

In some embodiments, the device 100 may include a click wheel as aninput control device 116. A user may navigate among and interact withone or more graphical objects (henceforth referred to as icons)displayed in the touch screen 112 by rotating the click wheel or bymoving a point of contact with the click wheel (e.g., where the amountof movement of the point of contact is measured by its angulardisplacement with respect to a center point of the click wheel. Theclick wheel may also be used to select one or more of the displayedicons. For example, the user may press down on at least a portion of theclick wheel or an associated physical button. User commands andnavigation commands provided by the user via the click wheel may beprocessed by an input controller 160 as well as one or more of themodules and/or sets of instructions in memory 102.

The device 100 also includes a power system 162 for powering the variouscomponents. The power system 162 may include a power management system,one or more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

The device 100 may also include one or more optical sensors 164. FIG. 1shows an optical sensor coupled to an optical sensor controller 158 inI/O subsystem 106. The optical sensor 164 may include charge-coupleddevice (CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. The optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with an imaging module144, the optical sensor 164 may capture still images or video. In someembodiments, an optical sensor is located on the back of the device 100,opposite the touch screen display 112 on the front of the device, sothat the touch screen display may be used as a viewfinder for eitherstill and/or video image acquisition. In some embodiments, an opticalsensor is located on the front of the device so that the user's imagemay be obtained for videoconferencing while the user views the othervideo conference participants on the touch screen display. In someembodiments, the position of the optical sensor 164 can be changed bythe user (e.g., by rotating the lens and the sensor in the devicehousing) so that a single optical sensor 164 may be used along with thetouch screen display for both video conferencing and still and/or videoimage acquisition.

The device 100 may also include one or more proximity sensors 166. FIG.1 shows a proximity sensor 166 coupled to the peripherals interface 118.Alternately, the proximity sensor 166 may be coupled to an inputcontroller 160 in the I/O subsystem 106. The proximity sensor 166 mayperform as described in U.S. patent application Ser. Nos. 11/241,839,“Proximity Detector In Handheld Device,” filed Sep. 30, 2005, and11/240,788, “Proximity Detector In Handheld Device,” filed Sep. 30,2005, which are hereby incorporated by reference. In some embodiments,the proximity sensor turns off and disables the touch screen 112 whenthe multifunction device is placed near the user's ear (e.g., when theuser is making a phone call). In some embodiments, the proximity sensorkeeps the screen off when the device is in the user's pocket, purse, orother dark area to prevent unnecessary battery drainage when the deviceis a locked state.

In some embodiments, the software components stored in memory 102 mayinclude an operating system 126, a communication module (or set ofinstructions) 128, a contact/motion module (or set of instructions) 130,a graphics module (or set of instructions) 132, a text input module (orset of instructions) 134, a Global Positioning System (GPS) module (orset of instructions) 135, and applications (or set of instructions) 136.

The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

The communication module 128 facilitates communication with otherdevices over one or more external ports 124 and also includes varioussoftware components for handling data received by the RF circuitry 108and/or the external port 124. The external port 124 (e.g., UniversalSerial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly toother devices or indirectly over a network (e.g., the Internet, wirelessLAN, etc.). In some embodiments, the external port is a multi-pin (e.g.,30-pin) connector that is the same as, or similar to and/or compatiblewith the 30-pin connector used on iPod (trademark of Apple Computer,Inc.) devices.

The contact/motion module 130 may detect contact with the touch screen112 (in conjunction with the display controller 156) and other touchsensitive devices (e.g., a touchpad or click wheel). The contact/motionmodule 130 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred, determining if there is movement of the contactand tracking the movement across the touch screen 112, and determiningif the contact has been broken (i.e., if the contact has ceased).Determining movement of the point of contact may include determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations may be applied to single contacts (e.g., onefinger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments, thecontact/motion module 130 and the display controller 156 also detectscontact on a touchpad. In some embodiments, the contact/motion module130 and the controller 160 detects contact on a click wheel.

The graphics module 132 includes various known software components forrendering and displaying graphics on the touch screen 112, includingcomponents for changing the intensity of graphics that are displayed. Asused herein, the term “graphics” includes any object that can bedisplayed to a user, including without limitation text, web pages, icons(such as user-interface objects including soft keys), digital images,videos, animations and the like. An animation in this context is adisplay of a sequence of images that gives the appearance of movement,and informs the user of an action that has been performed (such asmoving an email message to a folder). In this context, a respectiveanimation that confirms an action by the user of the device typicallytakes a predefined, finite amount of time, typically between 0.2 and 1.0seconds, and generally less than two seconds.

The text input module 134, which may be a component of graphics module132, provides soft keyboards for entering text in various applications(e.g., contacts 137, e-mail 140, IM 141, blogging 142, browser 147, andany other application that needs text input).

The GPS module 135 determines the location of the device and providesthis information for use in various applications (e.g., to telephone 138for use in location-based dialing, to camera 143 and/or blogger 142 aspicture/video metadata, and to applications that provide location-basedservices such as weather widgets, local yellow page widgets, andmap/navigation widgets).

The applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   a contacts module 137 (sometimes called an address book or        contact list);    -   a telephone module 138;    -   a video conferencing module 139;    -   an e-mail client module 140;    -   an instant messaging (IM) module 141;    -   a blogging module 142;    -   a camera module 143 for still and/or video images;    -   an image management module 144;    -   a video player module 145;    -   a music player module 146;    -   a browser module 147;    -   a calendar module 148;    -   widget modules 149, which may include weather widget 149-1,        stocks widget 149-2, calculator widget 149-3, alarm clock widget        149-4, dictionary widget 149-5, and other widgets obtained by        the user, as well as user-created widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;        and/or    -   search module 151.

Examples of other applications 136 that may be stored in memory 102include memo pad and other word processing applications, JAVA-enabledapplications, encryption, digital rights management, voice recognition,and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, the contactsmodule 137 may be used to manage an address book or contact list,including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers or e-mail addresses to initiate and/or facilitate communicationsby telephone 138, video conference 139, e-mail 140, or IM 141; and soforth. Embodiments of user interfaces and associated processes usingcontacts module 137 are described further below.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, the telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in theaddress book 137, modify a telephone number that has been entered, diala respective telephone number, conduct a conversation and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies. Embodiments of user interfaces andassociated processes using telephone module 138 are described furtherbelow.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contacts module 137, and telephone module138, the videoconferencing module 139 may be used to initiate, conduct,and terminate a video conference between a user and one or more otherparticipants.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the e-mail client module 140 may be used to create, send,receive, and manage e-mail. In conjunction with image management module144, the e-mail module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143. Embodiments ofuser interfaces and associated processes using e-mail module 140 aredescribed further below.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 may be used to enter asequence of characters corresponding to an instant message, to modifypreviously entered characters, to transmit a respective instant message(for example, using a Short Message Service (SMS) or Multimedia MessageService (MMS) protocol), to receive instant messages and to viewreceived instant messages. In some embodiments, transmitted and/orreceived instant messages may include graphics, photos, audio files,video files and/or other attachments as are supported in a MMS and/or anEnhanced Messaging Service (EMS). Embodiments of user interfaces andassociated processes using instant messaging module 141 are describedfurther below.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, image management module 144, and browsing module 147, theblogging module 142 may be used to send text, still images, video,and/or other graphics to a blog (e.g., the user's blog).

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, the camera module143 may be used to capture still images or video (including a videostream) and store them into memory 102, modify characteristics of astill image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, the image management module 144 may be used to arrange,modify or otherwise manipulate, label, delete, present (e.g., in adigital slide show or album), and store still and/or video images.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, audio circuitry 110, and speaker 111,the video player module 145 may be used to display, present or otherwiseplay back videos (e.g., on the touch screen or on an external, connecteddisplay via external port 124).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, the music player module146 allows the user to download and play back recorded music and othersound files stored in one or more file formats, such as MP3 or AACfiles. In some embodiments, the device 100 may include the functionalityof an MP3 player, such as an iPod (trademark of Apple Computer, Inc.).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the browser module 147 may be used to browse the Internet,including searching, linking to, receiving, and displaying web pages orportions thereof, as well as attachments and other files linked to webpages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail module 140, and browser module 147, the calendarmodule 148 may be used to create, display, modify, and store calendarsand data associated with calendars (e.g., calendar entries, to do lists,etc.).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134, thesearch module 151 may be used to search for text, music, sound, image,video, and/or other files in memory 102 that match one or more searchcriteria (e.g., one or more user-specified search terms).

Each of the above identified modules and applications correspond to aset of instructions for performing one or more functions describedabove. These modules (i.e., sets of instructions) need not beimplemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. In some embodiments, memory 102 maystore a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, the device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen 112 and/or a touchpad. By using a touch screenand/or a touchpad as the primary input/control device for operation ofthe device 100, the number of physical input/control devices (such aspush buttons, dials, and the like) on the device 100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates the device 100 to a main, home, or root menu from any userinterface that may be displayed on the device 100. In such embodiments,the touchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input/control device instead of a touchpad.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screen maydisplay one or more graphics. In this embodiment, as well as othersdescribed below, a user may select one or more of the graphics by makingcontact or touching the graphics, for example, with one or more fingers202 (not drawn to scale in the figure). In some embodiments, selectionof one or more graphics occurs when the user breaks contact with the oneor more graphics. In some embodiments, the contact may include agesture, such as one or more taps, one or more swipes (from left toright, right to left, upward and/or downward and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with the device 100. In some embodiments, inadvertentcontact with a graphic may not select the graphic. For example, a swipegesture with that sweeps over an application icon may not select thecorresponding application when the gesture corresponding to selection isa tap.

The device 100 may also include one or more physical buttons, such as“home” or menu button 204. As described previously, the menu button 204may be used to navigate to any application 136 in a set of applicationsthat may be executed on the device 100. Alternatively, in someembodiments, the menu button is implemented as a soft key in a GUI intouch screen 112.

In one embodiment, the device 100 includes a touch screen 112, a menubutton 204, a push button 206 for powering the device on/off and lockingthe device, and volume adjustment button(s) 208. The push button 206 maybe used to turn the power on/off on the device by depressing the buttonand holding the button in the depressed state for a predefined timeinterval; to lock the device by depressing the button and releasing thebutton before the predefined time interval has elapsed; and/or to unlockthe device or initiate an unlock process. In an alternative embodiment,the device 100 also may accept verbal input for activation ordeactivation of some functions through the microphone 113.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on a portablemultifunction device 100.

FIG. 3 illustrates an exemplary user interface for unlocking a portableelectronic device in accordance with some embodiments. In someembodiments, user interface 300 includes the following elements, or asubset or superset thereof:

-   -   Unlock image 302 that is moved with a finger gesture to unlock        the device;    -   Arrow 304 that provides a visual cue to the unlock gesture;    -   Channel 306 that provides additional cues to the unlock gesture;    -   Time 308;    -   Day 310;    -   Date 312; and    -   Wallpaper image 314.

In some embodiments, the device detects contact with the touch-sensitivedisplay (e.g., a user's finger making contact on or near the unlockimage 302) while the device is in a user-interface lock state. Thedevice moves the unlock image 302 in accordance with the contact. Thedevice transitions to a user-interface unlock state if the detectedcontact corresponds to a predefined gesture, such as moving the unlockimage across channel 306. Conversely, the device maintains theuser-interface lock state if the detected contact does not correspond tothe predefined gesture. As noted above, processes that use gestures onthe touch screen to unlock the device are described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, which is herebyincorporated by reference.

FIG. 4 illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator 402 for wireless communication;    -   Time 404;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Phone 138;        -   E-mail client 140, which may include an indicator 410 of the            number of unread e-mails;        -   Browser 147; and        -   Music player 146; and    -   Icons for other applications, such as:        -   IM 141;        -   Image management 144;        -   Camera 143;        -   Video player 145;        -   Weather 149-1;        -   Stocks 149-2;        -   Blog 142;        -   Calendar 148;        -   Calculator 149-3;        -   Alarm clock 149-4;        -   Dictionary 149-5; and        -   User-created widget 149-6.

In some embodiments, UI 400 displays all of the available applications136 on one screen so that there is no need to scroll through a list ofapplications (e.g., via a scroll bar). In some embodiments, as thenumber of applications increase, the icons corresponding to theapplications may decrease in size so that all applications may bedisplayed on a single screen without scrolling. In some embodiments,having all applications on one screen and a menu button enables a userto access any desired application with at most two inputs, such asactivating the menu button 204 and then activating the desiredapplication (e.g., by a tap or other finger gesture on the iconcorresponding to the application).

In some embodiments, UI 400 provides integrated access to bothwidget-based applications and non-widget-based applications. In someembodiments, all of the widgets, whether user-created or not, aredisplayed in UI 400. In other embodiments, activating the icon foruser-created widget 149-6 may lead to another UI (not shown) thatcontains the user-created widgets or icons corresponding to theuser-created widgets.

In some embodiments, a user may rearrange the icons in UI 400, e.g.,using processes described in U.S. patent application Ser. No.11/459,602, “Portable Electronic Device With Interface ReconfigurationMode,” filed Jul. 24, 2006, which is hereby incorporated by reference.For example, a user may move application icons in and out of tray 408using finger gestures.

In some embodiments, UI 400 includes a gauge (not shown) that displaysan updated account usage metric for an account associated with usage ofthe device (e.g., a cellular phone account), as described in U.S. patentapplication Ser. No. 11/322,552, “Account Information Display ForPortable Communication Device,” filed Dec. 23, 2005, which is herebyincorporated by reference.

FIG. 5 illustrates an exemplary user interface for listing instantmessage conversations on a portable multifunction device in accordancewith some embodiments. In some embodiments, user interface 500 includesthe following elements, or a subset or superset thereof:

-   -   402, 404, and 406, as described above;    -   “Instant Messages” or other similar label 502:    -   Names 504 of the people with whom a user is having instant        message conversations (e.g., Jane Doe 504-1) or the phone number        if the person's name is not available (e.g., 408-123-4567        504-3);    -   Text 506 of the last message in the conversation;    -   Date 508 and/or time of the last message in the conversation;    -   Selection icon 510 that when activated (e.g., by a finger tap on        the icon) initiates transition to a UI for the corresponding        conversation (e.g., FIG. 6A for Jane Doe 504-1);    -   Edit icon 512 that when activated (e.g., by a finger tap on the        icon) initiates transition to a UI for deleting conversations        (e.g., FIG. 7); and    -   Create message icon 514 that when activated (e.g., by a finger        tap on the icon) initiates transition to the users contact list        (e.g., FIG. 8A).

In some embodiments, the name 504 used for an instant messageconversation is determined by finding an entry in the user's contactlist 137 that contains the phone number used for the instant messageconversation. If no such entry is found, the phone number (of the otherparty with whom the user is exchanging messages) is displayed (e.g.,504-3). In some embodiments, if the other party sends messages from twoor more different phone numbers, the messages may appear as a singleconversation under a single name if all of the phone numbers used arefound in the same entry (i.e., the entry for the other party) in theuser's contact list 137.

Automatically grouping the instant messages into “conversations”(instant message exchanges with the same user or the same phone number)makes it easier for the user to carry on and keep track of instantmessage exchanges with multiple parties.

FIGS. 6A-6E illustrate an exemplary user interface for inputting textfor an instant message in accordance with some embodiments.

In some embodiments, user interface 600A includes the followingelements, or a subset or superset thereof:

-   -   402, 404, and 406, as described above;    -   Name 504 corresponding to the phone number used in the instant        message conversation (or the phone number itself if the name is        not available);    -   Instant messages icon 602 that when activated (e.g., by a finger        tap on the icon) initiates transition to a UI listing instant        message conversations (e.g., UI 500);    -   Instant messages 604 from the other party, typically listed in        order along one side of UI 600A;    -   Instant messages 606 to the other party, typically listed in        order along the opposite side of UI 600A to show the back and        forth interplay of messages in the conversation;    -   Timestamps 608 for at least some of the instant messages;    -   Text entry box 612;    -   Send icon 614 that when activated (e.g., by a finger tap on the        icon) initiates sending of the message in text box 612 to the        other party (e.g., Jane Doe 504-1);    -   Letter keyboard 616 for entering text in box 612;    -   Alternate keyboard selector icon 618 that when activated (e.g.,        by a finger tap on the icon) initiates the display of a        different keyboard (e.g., 624, FIG. 6C);    -   Send icon 620 that when activated (e.g., by a finger tap on the        icon) initiates sending of the message in text box 612 to the        other party (e.g., Jane Doe 504-1); and    -   Shift key 628 that when activated (e.g., by a finger tap on the        icon) capitalizes the next letter chosen on letter keyboard 616.

In some embodiments, a user can scroll through the message conversation(comprised of messages 604 and 606) by applying a vertical swipe gesture610 to the area displaying the conversation. In some embodiments, avertically downward gesture scrolls the conversation downward, therebyshowing older messages in the conversation. In some embodiments, avertically upward gesture scrolls the conversation upward, therebyshowing newer, more recent messages in the conversation. In someembodiments, as noted above, the last message in the conversation (e.g.,606-2) is displayed in the list of instant messages 500 (e.g., 506-1).

In some embodiments, keys in keyboards 616, 624, and/or 638 brieflychange shade and/or color when touched/activated by a user to help theuser learn to activate the desired keys.

In some embodiments, user interface 600B (FIG. 6B) includes thefollowing elements, or a subset or superset thereof:

-   -   402, 404, 406, 602, 604, 606, 608, 612, 614, 616, 618, and 620        as described above; and    -   word suggestion area 622 that provides a list of possible words        to complete the word fragment being typed by the user in box        612.

In some embodiments, the word suggestion area does not appear in UI 600Buntil after a predefined time delay (e.g., 2-3 seconds) in text beingentered by the user. In some embodiments, the word suggestion area isnot used or can be turned off by the user.

In some embodiments, user interface 600C (FIG. 6C) includes thefollowing elements, or a subset or superset thereof:

-   -   402, 404, 406, 602, 604, 606, 608, 612, 614, 620, and 622 as        described above;    -   Alternate keyboard 624, which may be made up primarily of digits        and punctuation; in some embodiments, frequently used        punctuation keys (e.g., period key 630, comma key 632, question        mark key 634, and exclamation point key 636) are larger than the        other keys of the keyboard 624;    -   Letter keyboard selector icon 626 that when activated (e.g., by        a finger tap on the icon) initiates the display of a letter        keyboard (e.g., 616, FIG. 6A); and    -   Shift key 628 that when activated (e.g., by a finger tap on the        icon) initiates display of yet another keyboard (e.g., 638, FIG.        6D).

In some embodiments, keeping the period key 630 near keyboard selectoricon 626 reduces the distance that a user's finger needs to travel toenter the oft-used period.

In some embodiments, user interface 600D (FIG. 6D) includes thefollowing elements, or a subset or superset thereof:

-   -   402, 404, 406, 602, 604, 606, 608, 612, 614, 620, 622, 626, 628        as described above; and    -   Another alternate keyboard 638, which may be made up primarily        of symbols and punctuation; in some embodiments, frequently used        punctuation keys (e.g., period key 630, comma key 632, question        mark key 634, and exclamation point key 636) are larger than the        other keys.

In some embodiments, user interface 600E (FIG. 6E) includes thefollowing elements, or a subset or superset thereof:

-   -   402, 404, 406, 602, 604, 606, 608, 612, 614, 616, 618, and 620,        as described above; and    -   New instant message 606-3 sent to the other party.

In some embodiments, when the user activates a send key (e.g., either614 or 620), the text in text box 612 “pops” or otherwise comes out ofthe box and becomes part of the string of user messages 606 to the otherparty. The black arrows in FIG. 6E illustrate an animated formation of aquote bubble 606-3. In some embodiments, the size of the quote bubblescales with the size of the message. In some embodiments, a sound isalso made when the message is sent, such as a droplet sound, to notifythe user.

FIG. 7 illustrates an exemplary user interface for deleting an instantmessage conversation in accordance with some embodiments. In someembodiments, user interface 700 includes the following elements, or asubset or superset thereof:

-   -   402, 404, 406, 504, 506, 508, 510, as described above;    -   Delete icons 702;    -   Remove icon 704; and    -   Done icon 706.

In some embodiments, if the user activates edit icon 512 (FIG. 5), thedelete icons 702 appear next to each instant message conversation. If auser activates a delete icon (e.g., by tapping it with a finger), theicon may rotate 90 degrees (e.g., 702-4) or otherwise change itsappearance and/or a second icon may appear (e.g., remove icon 704). Ifthe user activates the second icon, the corresponding instant messageconversation is deleted.

This deletion process, which requires multiple gestures by the user ondifferent parts of the touch screen (e.g., delete icon 702-4 and removeicon 704 are on opposite sides of the touch screen) greatly reduces thechance that a user will accidentally delete a conversation or othersimilar item.

The user activates the done icon 706 (e.g., by tapping on it with afinger) when the user has finished deleting IM conversations and thedevice returns to UI 500.

If there is a long list of conversations (not shown) that fill more thanthe screen area, the user may scroll through the list using verticallyupward and/or vertically downward gestures 708 on the touch screen.

FIGS. 8A and 8B illustrate an exemplary user interface for a contactlist in accordance with some embodiments.

In some embodiments, user interfaces 800A and 800B include the followingelements, or a subset or superset thereof:

-   -   402, 404, 406, as described above;    -   Groups icon 802 that when activated (e.g., by a finger tap on        the icon) initiates display of groups of contacts;    -   First name icon 804 that when activated (e.g., by a finger tap        on the icon) initiates an alphabetical display of the user's        contacts by their first names (FIG. 8B);    -   Last name icon 806 that when activated (e.g., by a finger tap on        the icon) initiates an alphabetical display of the user's        contacts by their last names (FIG. 8A);    -   Alphabet list icons 808 that the user can touch to quickly        arrive at a particular first letter in the displayed contact        list;    -   Cancel icon 810 that when activated (e.g., by a finger tap on        the icon) initiates transfer back to the previous UI (e.g., UI        500); and    -   Other number icon 812 that when activated (e.g., by a finger tap        on the icon) initiates transfer to a UI for entering a phone        number for instant messaging, such as a phone number that is not        in the user's contact list (e.g., UI 900, FIG. 9).

As described in U.S. patent application Ser. No. 11/322,547, “ScrollingList With Floating Adjacent Index Symbols,” filed Dec. 23, 2005, whichis hereby incorporated by reference, the user may scroll through thecontact list using vertically upward and/or vertically downward gestures814 on the touch screen.

FIG. 9 illustrates an exemplary user interface for entering a phonenumber for instant messaging in accordance with some embodiments. Insome embodiments, user interface 900 includes the following elements, ora subset or superset thereof:

-   -   402, 404, 406, 602, and 624, as described above;    -   Cancel icon 902 that when activated (e.g., by a finger tap on        the icon) initiates transfer back to the previous UI (e.g., UI        800A or UI 800B);    -   Save icon 904 that when activated (e.g., by a finger tap on the        icon) initiates saving the entered phone number in the instant        messages conversation list (e.g., UI 500) and displaying a UI to        compose an instant message to be sent to the entered phone        number (e.g., UI 600A); and    -   Number entry box 906 for entering the phone number using        keyboard 624.

Note that the keyboard displayed may depend on the application context.For example, the UI displays a soft keyboard with numbers (e.g., 624)when numeric input is needed or expected. The UI displays a softkeyboard with letters (e.g., 616) when letter input is needed orexpected.

FIGS. 10A-10M illustrate an exemplary user interface for displaying andmanaging contacts in accordance with some embodiments.

In some embodiments, in response to the user activating phone icon 138in UI 400 (FIG. 4) (e.g., by a finger tap on the icon), the user'scontact list is displayed (e.g., UI 2600A, FIG. 10A).

As described in U.S. patent application Ser. No. 11/322,547, “ScrollingList With Floating Adjacent Index Symbols,” filed Dec. 23, 2005, whichis hereby incorporated by reference, the user may scroll through thecontact list using vertically upward and/or vertically downward gestures2602 on the touch screen.

In some embodiments, in response to the user activating add new contacticon 2604 (e.g., by a finger tap on the icon), the touch screen displaysa user interface for editing the name of the contact (e.g., UI 2600B,FIG. 10B).

In some embodiments, in response to the user entering the contact name(e.g., entering “Ron Smith” via keyboard 616 in UI 2600C, FIG. 10C) andactivating the save icon 2606 (e.g., by a finger tap on the icon), thecontacts module creates and displays a new entry for the contact (e.g.,UI 2600D, FIG. 10D).

In some embodiments, in response to the user activating add new phoneicon 2608 (e.g., by a finger tap on the icon or on the row containingthe icon), the touch screen displays a user interface for editing thephone number(s) of the contact (e.g., UI 2600E, FIG. 10E).

In some embodiments, in response to the user entering the phone number(e.g., via keyboard 624 in UI 2600E, FIG. 10E); specifying the type ofphone number (e.g., by a tap or other predefined gesture on mobile icon2618, home icon 2620, or work icon 622); and activating the save icon2618 (e.g., by a finger tap on the icon), the contacts module creates aphone number for the corresponding contact.

In some embodiments, the user can select additional phone number types.For example, in response to the user activating selection icon 2624(e.g., by a finger tap on the icon), the touch screen displays a phonelabel UI (e.g., UI 2600F, FIG. 10F). In some embodiments, in response tothe user activating a label in UI 2600F, the chosen label is displayedin place of work icon 2622 in UI 2600E. In some embodiments, the chosenlabel is also highlighted in UI 2600E to indicate to the user that thephone number being entered will be given the chosen label.

In some embodiments, the user can add custom phone labels to UI 2600F byactivating an add labels icon 2628 and entering the label via a softkeyboard (e.g., 616, not shown).

In some embodiments, the user can delete one or more of the labels in UI2600F. In some embodiments, only the user's custom labels may bedeleted. For example, in response to the user activating the edit icon2630 (e.g., by a finger tap on the icon), the touch screen displays adelete icon 2632 next to the labels that may be deleted (e.g., UI 2600G,FIG. 10G). If a user activates a delete icon (e.g., by tapping it with afinger), the icon may rotate 90 degrees (e.g., 2634, FIG. 10H) orotherwise change its appearance and/or a second icon may appear (e.g.,remove icon 2636, FIG. 10H). If the user activates the second icon, thecontact module deletes the corresponding label. This deletion process isanalogous to the process described above with respect to FIG. 7. Asnoted above, a deletion process that requires multiple gestures by theuser on different parts of the touch screen (e.g., delete icon 2632 andremove icon 2636 are on opposite sides of the touch screen in UI 2600H)greatly reduces the chance that a user will accidentally delete a labelor other similar item. The user activates the done icon 2638 (e.g., bytapping on it with a finger) when the user has finished deleting labelsand the device returns to UI 2600F.

In some embodiments, in response to the user activating add new emailicon 2610 (FIG. 10D) (e.g., by a finger tap on the icon or on the rowcontaining the icon), the touch screen displays a user interface forediting the email address(es) of the contact (e.g., UI 26001, FIG. 10I).

In some embodiments, in response to the user entering the email address(e.g., via keyboard 616 in UI 26001, FIG. 10I); specifying the type ofemail address (e.g., by a tap or other predefined gesture on home icon2640, work icon 2642, or other icon 2644); and activating the save icon2648 (e.g., by a finger tap on the icon), the contacts module creates anemail address for the corresponding contact.

In some embodiments, the user can select additional email address typesby activating selection icon 2646; add custom email address types,and/or delete email address types using processes and UIs analogous tothose described for phone number types (FIGS. 10E-10H).

In some embodiments, in response to the user activating add new addressicon 2612 (FIG. 10D) (e.g., by a finger tap on the icon or on the rowcontaining the icon), the touch screen displays a user interface forediting the physical address(es) of the contact (e.g., UI 2600J, FIG.10J).

In some embodiments, in response to the user entering the address (e.g.,via keyboard 616 in UI 2600J, FIG. 10J); specifying the type of address(e.g., by a tap or other predefined gesture on home icon 2650, work icon2652, or other icon 2654); and activating the save icon 2658 (e.g., by afinger tap on the icon), the contacts module creates an address for thecorresponding contact.

In some embodiments, the user can select additional address types byactivating selection icon 2656; add custom address types, and/or deleteaddress types using processes and UIs analogous to those described forphone number types (FIGS. 10E-10H).

In some embodiments, in response to the user activating add new ringtoneicon 2614 (FIG. 10D) (e.g., by a finger tap on the icon or on the rowcontaining the icon), the touch screen displays a user interface forselecting ringtones (e.g., UI 2600K, FIG. 10K).

In some embodiments, in response to the user selecting a ringtone (e.g.,by tap or other predefined gesture on the ringtone or the row containingthe ringtone) and activating the save icon 2660 (e.g., by a finger tapon the icon), the contacts module assigns a ringtone to thecorresponding contact.

In some embodiments, the user can add new ringtones by activating addicon 2662.

In some embodiments, a thumbnail image or other graphic 2616 (FIG. 10D)can be added for the contact.

FIG. 10L illustrates an exemplary user interface for an existing contactlist entry in accordance with some embodiments. In response to the userselecting edit icon 2664 (e.g., by a finger tap on the icon), the touchscreen displays a user interface for editing the contact (e.g., UI2600M, FIG. 10M). In response to user selections, the contact listmodule may delete one or more items of existing contact information, addnew phone numbers, add new email addresses, add new physical addresses,and/or add new ringtones using the processes and UIs described above(e.g., FIGS. 10E-10K).

FIGS. 11A-11C illustrate an exemplary user interface for displaying andmanaging favorite contacts in accordance with some embodiments. UI 2700A(FIG. 11A) displays an exemplary list of favorites. In some embodiments,each row in the list that corresponds to a favorite includes the name2702 of the favorite, the type of phone number 2704 for the favoritethat will be called, and an additional information icon 2706. In someembodiments, in response to the user activating icon 2706 for aparticular favorite (e.g., by a finger tap on the icon), the touchscreen displays the corresponding contact list entry for that favorite(e.g., UI 2600L, FIG. 10L). In some embodiments, in response to a usertap or other predefined gesture elsewhere (i.e., a tap or gesture otherthan on icon 2702) in the row corresponding to a particular favorite,the phone module dials the corresponding phone number 2704 for thatparticular favorite.

In some embodiments, in response to the user activating add favoriteicon 2708 (e.g., by a finger tap on the icon), the device displays theuser's contact list, from which the user selects the contact list entryfor a new favorite and a phone number in the entry for the new favorite.

In response to the user activating the edit icon 2710 (e.g., by a fingertap on the icon), the touch screen displays a delete icon 2712 next tothe favorites (e.g., UI 2700B, FIG. 11B). If a user activates a deleteicon (e.g., by tapping it with a finger), the icon may rotate 90 degrees(e.g., 2714, FIG. 11C) or otherwise change its appearance and/or asecond icon may appear (e.g., remove icon 2716, FIG. 11C). If the useractivates the second icon, the corresponding favorite is deleted. Thisdeletion process is analogous to the process described above withrespect to FIGS. 7, 10G and 10H. As noted above, a deletion process thatrequires multiple gestures by the user on different parts of the touchscreen (e.g., delete icon 2714 and remove icon 2716 are on oppositesides of the touch screen in UI 2700C) greatly reduces the chance that auser will accidentally delete a favorite or other similar item. The useractivates the done icon 2718 (e.g., by tapping on it with a finger) whenthe user has finished deleting favorites and the device returns to UI2700A.

FIGS. 12A-12D illustrate an exemplary user interface for displaying andmanaging recent calls in accordance with some embodiments.

In some embodiments, in response to the user activating All icon 2810,the touch screen displays a list of all recent calls (e.g., UI 2800A,FIG. 12A). In some embodiments, in response to the user activatingMissed icon 2812, the touch screen displays a list of recent missedcalls (e.g., UI 2800B, FIG. 12B). The handling of missed calls isdescribed further below with reference to FIGS. 23-25. The handling oftelephone call information including recent calls is described furtherbelow with reference to FIGS. 26-27.

In some embodiments, each row in a list corresponds to a call or aconsecutive sequence of calls involving the same person or the samenumber (without an intervening call involving another person or anotherphone number). In some embodiments, each row includes: the name 2802 ofthe other party (if available via the contact module) or the phonenumber (if the name of the other party is not available); the number2804 of consecutive calls (in an exemplary embodiment, number 2804 isnot displayed if the number of consecutive calls is equal to one); thedate and/or time 2806 of the last call; and an additional informationicon 2808. In some embodiments, in response to the user activating icon2808 for a particular row (e.g., by a finger tap on the icon), the touchscreen displays the corresponding contact list entry for the other party(e.g., UI 2800C, FIG. 12C) or UI 2800D (FIG. 12D) if the phone numbercannot be associated with an entry in the user's contact list. In someembodiments, in response to a user tap or other predefined gestureelsewhere (i.e., a tap or gesture other than on icon 2808) in a givenrow, the phone module dials the corresponding phone number for that row.

In some embodiments, some rows may include icons indicating whether thelast call associated with the row was missed or answered.

If the list of recent calls fills more than the screen area, the usermay scroll through the list using vertically upward and/or verticallydownward gestures 2814 on the touch screen.

In some embodiments, UI 2800C highlights (e.g., with color, shading,and/or bolding) the phone number associated with the recent call (e.g.,the two recent incoming calls from Bruce Walker in UI 2800A came fromBruce Walker's work number 2816). In some embodiments, in response to auser tap or other predefined gesture on the highlighted number 2816, thephone module dials the highlighted number (e.g., 2816). In someembodiments, in response to a user tap or other predefined gesture onanother number in the contact list entry (e.g., home number 2818), thephone module dials the corresponding number. In some embodiments, inresponse to a user tap or other predefined gesture on an email addressin the contact list entry (e.g., either work email 2820 or home email2822), the mail module prepares an email message with the selected emailaddress, ready for text input by the user. In some embodiments, inresponse to a user tap or other predefined gesture on an instant messageobject corresponding to a telephone number (not shown), the instantmessage module prepares an instant message to the correspondingtelephone number, ready for text input by the user. Thus, by selectingicon 2808 (FIG. 12A) in the Recent Calls UI 2800C, the user may easilyrespond to a caller using the same number involved in the previous call(e.g., 2816), another number associated with the same caller (e.g.,2818), or another mode of communication besides the phone (e.g., anemail to the caller's work 2820 or home 2822 email address).

In some embodiments, UI 2800D provides one or more options for a user tomake use of a phone number in a recent call that is not associated withan entry in the user's contact list. In some embodiments, in response toa tap or other predefined user gesture, the device may: call the phonenumber (e.g., if the gesture is applied to icon 2824); create a newcontact with the phone number (e.g., if the gesture is applied to icon2826); add the phone number to an existing contact (e.g., if the gestureis applied to icon 2828); or check the call history associated with thenumber (e.g., if the gesture is applied to icon 2830).

FIG. 13 illustrates an exemplary dial pad interface for calling inaccordance with some embodiments. In response to the user activating thenumber keys in dial pad 2902 (e.g., by finger taps on the number icons),the touch pad displays the selected digits 2904. In some embodiments,the phone module automatically adds the parentheses and dashes to theselected digits to make the number easier to read. In response to theuser activating the call icon 2906, the phone module dials or transmitsthe selected digits.

FIGS. 14A-14D illustrate exemplary user interfaces displayed during acall in accordance with some embodiments. In some embodiments, the UIindicates that a call is being attempted 3002 (UI 3000A, FIG. 14A and UI3000C, FIG. 14C) and then indicates the connection time 3004 after theconnection is made (UI 3000B, FIG. 14B and UI 3000D, FIG. 14D).

In some embodiments, in response to a tap or other predefined usergesture,

the device may: mute the call (e.g., if the gesture is applied to icon3006); place the call on hold (e.g., if the gesture is applied to icon3008); place the call on a speaker (e.g., if the gesture is applied toicon 3010); setup a conference call (e.g., if the gesture is applied toconference icon 3012, FIGS. 14A-14B or to add call icon 3018, FIGS.14C-14D); display a keypad (e.g., if the gesture is applied to icon3016); display a contacts list (e.g., if the gesture is applied to icon3020); or end the call (e.g., if the gesture is applied to icon 3014).Display of corresponding items in the user interface is furtherdescribed below with regard to process 5600 (FIG. 29).

FIGS. 15A and 15B illustrate an exemplary user interface displayedduring an incoming call in accordance with some embodiments.

In some embodiments, if the incoming call is from a phone number that isassociated with a person or other entry in the user's contact list, thenthe touch screen may display: the name 3102 of the person or entry; agraphic 3104 associated with the person or entry; a Decline icon 3106that when activated (e.g., by a finger tap on the icon) causes the phonemodule to decline the call and/or initiate voicemail for the call; andan answer icon 3108 that when activated (e.g., by a finger tap on theicon) causes the phone module to answer the call (e.g., UI 3100A, FIG.15A). Display of these items is further described below with regard toprocess 5500 (FIG. 28).

In some embodiments, if the incoming call is from a phone number that isnot associated with a person or other entry in the user's contact list,then the touch screen may display: the phone number of the other party3110; a Decline icon 3106 that when activated (e.g., by a finger tap onthe icon) causes the phone module to decline the call and/or initiatevoicemail for the call; and an answer icon 3108 that when activated(e.g., by a finger tap on the icon) causes the phone module to answerthe call (e.g., UI 3100B, FIG. 15B).

In some embodiments, the device pauses some other applications (e.g.,the music player 146, video player, and/or slide show) when there is anincoming call; displays UI 3100A or UI 3100B prior to the call beinganswered; displays UI 3000B during the call; and terminates the pause onthe other applications if the incoming call is declined or the callends. In some embodiments, there is a smooth transition into and out ofa pause (e.g., a smooth lowering and raising of the sound volume for themusic player).

FIGS. 16A and 16B illustrate an exemplary user interface for voicemailin accordance with some embodiments. In some embodiments, userinterfaces 3200A and 3200B include the following elements, or a subsetor superset thereof:

-   -   402, 404, and 406, as described above;    -   backup icon 3202 that when activated (e.g., by a finger tap on        the icon) initiates a process that backs up and replays the        preceding few seconds of the voicemail message;    -   Progress bar 3204 that indicates what fraction of a voicemail        message has been played and that may be used to help scroll        through the message in response to a user gesture 3206;    -   Speed up icon 3208 that when activated (e.g., by a finger tap on        the icon) initiates a process that speeds up playback of the        voicemail message, which may also adjust the sound frequency or        pitch of the fast playback so that the words, although spoken        quickly, are still easy to understand:    -   Names 3210 of the people (associated with incoming phone numbers        via the user's contact list) who have left voicemail messages        (e.g., Aaron Jones 3210-1) or the phone number if the person's        name is not available (e.g., 408-246-8101 3210-3);    -   Date 3212 and/or time of the voicemail;    -   Additional information icon 3214 that when activated (e.g., by a        finger tap on the icon) initiates transition to the        corresponding contact list entry (e.g., UI 2800C, FIG. 12C) or        to a UI for unknown phone numbers (e.g., UI 2800D, FIG. 12D);    -   Speaker icon 3216 that when activated (e.g., by a finger tap on        the icon) initiates playback of the voicemail through a speaker;    -   Options icon 3218 that when activated (e.g., by a finger tap on        the icon) initiates display of a menu of additional voicemail        options;    -   Pause icon 3220 that when activated (e.g., by a finger tap on        the icon) initiates pausing of the voicemail;    -   Delete symbol icon 3222 that when activated (e.g., by a finger        tap on the icon) initiates display of a UI to confirm that the        user wants to delete the corresponding voicemail (e.g., UI        3200B, FIG. 16B).    -   Cancel icon 3226 that when activated (e.g., by a finger tap on        the icon) changes the display from UI 3200B to UI 3200A without        canceling the corresponding voicemail;    -   Delete icon 3228 that when activated (e.g., by a finger tap on        the icon) deletes the corresponding voicemail and changes the        display from UI 3200B to UI 3200A; and    -   Play icon 3230 that when activated (e.g., by a finger tap on the        icon) initiates or continues playback of the voicemail.

If the list of voicemail messages fills more than the screen area, theuser may scroll through the list using vertically upward and/orvertically downward gestures 3224 on the touch screen.

In some embodiments, in response to a user tap or other predefinedgesture in the row corresponding to a particular voicemail (but otherthan a tap or gesture on icon 3214), the phone module initiates playbackof the corresponding voicemail. Thus, there is random access to thevoicemails and the voicemails may be heard in any order.

In some embodiments, in response to a user gesture, the playbackposition in the voicemail can be modified. For example, in response tothe user's finger touching 3206 at or near the current playback positionwithin the progress bar and then sliding along the progress bar, theplayback position may be altered to correspond to the position of theuser's finger along the progress bar. This user gesture on the progressbar makes it easy for a user to skip to and/or replay portions ofinterest in the voicemail message.

FIG. 17 illustrates an exemplary user interface for organizing andmanaging email in accordance with some embodiments. In some embodiments,user interface 3300 includes the following elements, or a subset orsuperset thereof:

-   -   402, 404, and 406, as described above;    -   a set of mailboxes, such as inbox 3302, which may be organized        in rows with a selection icon 3306 for each row;    -   a settings icon 3308 that when activated (e.g., by a finger tap        on the icon) initiates display of a UI to input mailbox settings        (e.g., UI 3600, FIG. 20); and    -   a create email icon 3310 that when activated (e.g., by a finger        tap on the icon) initiates display of a UI for creating a new        email message (e.g., UI 3400, FIG. 18).

If the set of mailboxes fills more than the screen area, the user mayscroll through the mailboxes using vertically upward and/or verticallydownward gestures 3312 on the touch screen.

FIGS. 18A and 18B illustrate an exemplary user interface for creatingemails in accordance with some embodiments.

In response to the user activating create email icon 3310 (UI 3300, FIG.17), the device displays UI 3400A.

In some embodiments, if the user makes a tap or other predefined gestureon the subject line 3408 or in the body of the email 3412 (FIG. 18A), aletter keyboard 616 appears and the user may input the subject and/orbody text (FIG. 18B). In some embodiments, to enter the email address,the user makes a tap or other predefined gesture on the To: line 3406 ofthe email; the user's contact list appears (e.g., FIG. 8A); the usermakes a tap or other predefined gesture on the desiredrecipient/contact; and the device places the corresponding email addressin the email message (FIG. 18B). In some embodiments, the user may alsoenter the email address using one or more keyboards (e.g., 616 and 624,not shown). The device sends the email message in response to the useractivating the send icon 3404 (FIG. 18B) (e.g., by a finger tap on theicon). Alternatively, if the user activates the cancel icon 3402, thedevice may display a save draft icon and a don't save icon (not shown).The device saves the draft if the user activates the save draft icon,e.g., in a drafts folder in mail client 140 (FIG. 17). The devicedeletes the draft if the user activates the don't save icon.

In some embodiments, in response to the user activating the attach icon3410 (e.g., by a finger tap on the icon), the touch screen displays a UIfor adding attachments (not shown).

FIGS. 19A-19F illustrate an exemplary user interface for displaying andmanaging an inbox in accordance with some embodiments. An analogous userinterface may be used to display and manage the other mailboxes (e.g.,drafts, sent, trash, personal, and/or work in UI 3300). In someembodiments, user interfaces 3500A-3500F include the following elements,or a subset or superset thereof:

-   -   402, 404, 406, and 3310, as described above;    -   mailboxes icon 3502 that when activated (e.g., by a finger tap        on the icon) initiates the display of mailbox UI 3300 (FIG. 17);    -   unread messages icon 3504 that displays the number of unread        messages in the inbox;    -   names 3506 of the senders of the email messages;    -   subject lines 3508 for the email messages;    -   dates 3510 of the email messages;    -   unread message icons 3512 that indicate messages that have not        been opened;    -   preview pane separator 3518 that separates the list of messages        from a preview of a selected message in the list;    -   settings icon 3520 that when activated (e.g., by a finger tap on        the icon) initiates the display of settings UI 3600 (FIG. 20);    -   move message icon 3522 that when activated (e.g., by a finger        tap on the icon) initiates the display of move message UI 3800A        (FIG. 22);    -   Delete symbol icon 3524 that when activated (e.g., by a finger        tap on the icon) initiates display of a UI to confirm that the        user wants to delete the selected email (e.g., UI 3500E, FIG.        19E);    -   Reply/Forward icon 3526 that when activated (e.g., by a finger        tap on the icon) initiates display of a UI to select how to        reply or forward the selected email (e.g., UI 3500F, FIG. 19F);    -   Preview pane 3528 that displays a portion of the selected email        message;    -   Details icon 3530 that when activated (e.g., by a finger tap on        the icon) initiates display of email addressing details 3534        (FIG. 19C);    -   Cancel icon 3540 that when activated (e.g., by a finger tap on        the icon) returns the device to the previous user interface        (e.g., UI 3500D);    -   Delete icon 3542 that when activated (e.g., by a finger tap on        the icon) deletes the selected email;    -   Reply icon 3544 that when activated (e.g., by a finger tap on        the icon) initiates creation of an email replying to the sender;    -   Reply All icon 3546 that when activated (e.g., by a finger tap        on the icon) initiates creation of an email replying to the        sender and the other parties included in the selected email        (e.g., by cc:);    -   Forward icon 3548 that when activated (e.g., by a finger tap on        the icon) initiates creation of an email to be forwarded;

If the set of emails fill more than the screen area (or more than thescreen area above the preview pane), the user may scroll through theemails using vertically upward and/or vertically downward gestures 3514on the touch screen.

In some embodiments, the email subjects 3508 are not displayed if thepreview pane 3528 is used (as shown in FIGS. 19B-19F). In someembodiments, the position of the preview pane separator can be adjusted(see FIG. 19A) by the user making contact 3516 at or near the previewpane separator and moving the separator to the desired location bydragging the finger contact 3538. In some embodiments, arrows 3539 orother graphics appear during the positioning of the preview paneseparator (e.g., UI 3500D, FIG. 19D) to help guide the user.

In some embodiments, in response to a tap or other predefined gesture bythe user in a row containing information (e.g., 3506, 3510, and/or 3508)about a particular email message, some or all of the text in the row ishighlighted (e.g., by coloring, shading, or bolding) and thecorresponding message is displayed in the preview pane area. In someembodiments, in response to a tap or other predefined gesture by theuser in a row containing information (e.g., 3506, 3510, and/or 3508)about a particular email message, the email message is displayed on thefull screen if the preview pane is not being used.

In some embodiments, if the selected email fills more than the previewpane area, the user may scroll through the email using two-dimensionalgestures 3532 in the preview pane with vertical and/or horizontalmovement of the email on the touch screen.

In some embodiments, in response to user activation of an additionalinformation icon (e.g., “>”) on the detail information 3534 (e.g., by afinger tap 3536 on the icon), the touch screen may display contact listinformation for the corresponding party, if available (e.g., UI 2800C,FIG. 12C) or a UI analogous to UI 2800D, FIG. 12D.

FIG. 20 illustrates an exemplary user interface for setting email userpreferences in accordance with some embodiments. In some embodiments,user interface 3600 includes the following elements, or a subset orsuperset thereof:

-   -   402, 404, and 406, as described above;    -   Done icon 3602 that when activated (e.g., by a finger tap on the        icon) returns the device to the previous UI;    -   Accounts 3604 for entering email account information;    -   Message list displays 3606 for selecting whether sender 3506        and/or subject 3508 information is displayed in the emails        lists;    -   Display newest messages 3608 for selecting whether the newest        messages are displayed at the top or bottom of the screen;    -   Message display locations 3610 for selecting whether the        messages are displayed in the preview pane or full screen;    -   Preferred message format 3612 for selecting how the messages are        formatted (e.g., HTML or plain text);    -   Rules 3614 for creating rules for managing email messages (e.g.,        using UI 3700A, FIG. 21A, and UI 3700B, FIG. 21B);    -   Selection icons 3616 that when activated (e.g., by a finger tap        on the icon) show choices for the corresponding settings.

In some embodiments, a user may tap anywhere in the row for a particularsetting to initiate display of the corresponding setting choices.

FIGS. 21A and 21B illustrate an exemplary user interface for creatingand managing email rules in accordance with some embodiments. In someembodiments, user interface 3700A includes the following elements, or asubset or superset thereof:

-   -   402, 404, and 406, as described above;    -   Settings icon 3702 that when activated (e.g., by a finger tap on        the icon) returns the device to the settings UI 3600 (FIG. 20);    -   Rules 3704;    -   Selection icons 3706 that when activated (e.g., by a finger tap        on the icon) show choices for the corresponding rules.    -   Add icon 3708 that when activated (e.g., by a finger tap on the        icon) displays a UI for creating a new rule (e.g., UI 3700B,        FIG. 21B);    -   Done icon 3710 that when activated (e.g., by a finger tap on the        icon) returns the device to the settings UI 3600 (FIG. 20);

In some embodiments, a user may tap anywhere in the row for a particularrule to initiate display of the corresponding rule (e.g., UI 3700B, FIG.21B).

FIGS. 22A and 22B illustrate an exemplary user interface for movingemail messages in accordance with some embodiments.

In response to the user activating move message icon 3522 (see UI 3500A,FIG. 19A), the device displays UI 3800A, with some information 3804 forthe selected message displayed.

In some embodiments, if the user makes a tap 3802 or other predefinedgesture on a row corresponding to a particular mailbox or other folder,the message is moved to the corresponding mailbox or folder (e.g., Workin FIG. 22A). In some embodiments, the selected row is highlighted andan animation appears to move the message information 3804 into theselected row (as illustrated schematically in FIG. 22B).

FIG. 23 is a flow diagram illustrating a process 5000 for handlingmissed telephone calls at a portable electronic device with a touchscreen display in accordance with some embodiments. A list of itemscomprising missed telephone calls is displayed (5002). For example, UI2800B (FIG. 12B) displays a list of missed calls. In some embodiments, asingle item in the list of items corresponds to a plurality of missedtelephone calls (5004). In some embodiments, information indicating anumber of missed calls is displayed in a respective single item in thelist (5006). For example, the top item in UI 2800B for Bruce Walker 2803corresponds to two missed telephone calls, as indicated by the number2805. In some embodiments, the plurality of calls corresponding to thesingle item are consecutive in time. In some embodiments, a single itemin the list of items corresponds to a plurality of missed telephonecalls from a plurality of distinct telephone numbers associated with arespective caller (5008). Displaying a single item in the list of itemsthat corresponds to a plurality of missed telephone calls condenses themissed call list and makes it easy for a user to determine which peopleare trying to contact the user and how many times they have tried tocontact the user.

In some embodiments, a scrolling gesture comprising substantiallyvertical movement of a user contact with the touch screen display isdetected (5010). In response, the displayed list of items is scrolled(5012). For example, the list of items displayed in UI 2800B is scrolledin response to vertical gesture 2814 (FIG. 12B). The scrolling gestureprovides a simple way for the user to rapidly scan the list of items.

Upon detecting user selection of an item in the list (5014), contactinformation is displayed for a respective caller corresponding to theuser-selected item (5016). For example, if a user selects the item forBruce Walker 2803 in UI 2800B (FIG. 12B), contact information for BruceWalker is displayed in UI 2800C (FIG. 12C). The contact informationincludes a plurality of contact objects. The plurality of contactobjects include a first contact object, comprising a telephone numberobject having a first telephone number associated with the missedtelephone call, and a second contact object. In some embodiments, thesecond contact object is an email contact object. In some embodiments,the second contact object is a telephone number object having a secondtelephone number different from the first telephone number. In someembodiments, the second contact object is an instant messaging object.In the example of FIG. 12C, work telephone number 2816, from which thetwo missed calls were made, corresponds to the first contact object. Anyof objects 2818, 2820, and 2822 could correspond to the second contactobject.

Upon detecting user selection of the second contact object (5018), acommunication is initiated with the respective caller via a modalitycorresponding to the second contact object (5020). In some embodiments,in which the second contact object is an email contact object, themodality corresponding to the second contact object includes sending anemail message. For example, user selection of object 2820 in UI 2800C(FIG. 12C) would initiate an email to Bruce Walker's work email address.In some embodiments, in which the second contact object is a telephonenumber object having a second telephone number different from the firsttelephone number, the modality corresponding to the second contactobject includes initiating a telephone call to the second telephonenumber. For example, user selection of object 2818 in UI 2800C wouldinitiate a telephone call to Bruce Walker's home number. In someembodiments, in which the second contact object is an instant messagingobject, the modality corresponding to the second contact object includessending an instant message. Providing a plurality of contact objectsmakes it easy for a user to choose and initiate communications with themissed caller by any available communication modality, rather than beinglimited to calling back the missed caller at the phone number associatedwith the missed call. For example, rather than calling Bruce Walker backat his work number, a user can just as easily call Bruce at home or sendBruce an email message.

While the missed telephone call handling process 5000 described aboveincludes a number of operations that appear to occur in a specificorder, it should be apparent that the process 5000 can include more orfewer operations, which can be executed serially or in parallel (e.g.,using parallel processors or a multi-threading environment), an order oftwo or more operations may be changed and/or two or more operations maybe combined into a single operation. For example, operations 5010 and5012 may be omitted if the item to be selected in operation 5014 isdisplayed initially in operation 5002.

FIG. 24 is a flow diagram illustrating a process 5100 for handlingmissed telephone calls at a portable electronic device with a touchscreen display in accordance with some embodiments. A list of itemscomprising missed telephone calls is displayed (5002), as describedabove with regard to process 5000 (FIG. 23). In some embodiments, asingle item in the list of items corresponds to a plurality of missedtelephone calls (5004). In some embodiments, information indicating anumber of missed calls is displayed in a respective single item in thelist of items (5006). In some embodiments, a single item in the list ofitems corresponds to a plurality of missed telephone calls from aplurality of distinct telephone numbers associated with a respectivecaller (5008). Displaying a single item in the list of items thatcorresponds to a plurality of missed telephone calls condenses themissed call list and makes it easy for a user to determine which peopleare trying to contact the user and how many times they have tried tocontact the user.

In some embodiments, a scrolling gesture comprising substantiallyvertical movement of a user contact with the touch screen display isdetected. In response, the displayed list of items is scrolled (notshown). The scrolling gesture provides a simple way for the user torapidly scan the list of items.

Upon detecting finger contact with a first portion of a user-selecteditem in the list (5110), a return telephone call is initiated to areturn telephone number associated with the user-selected item (5112).In some embodiments, for example, in response to a tap or otherpredefined gesture on a row in UI 2800B (FIG. 12B) other than on icon2808, a return telephone call is initiated to the corresponding numberfor that row.

Upon detecting finger contact with a second portion of the respectiveitem in the list (5114), contact information is displayed for arespective caller corresponding to the user-selected item (5116). Thecontact information includes a plurality of contact objects. Theplurality of contact objects include a first contact object, comprisinga telephone number object having the return telephone number, and asecond contact object. In some embodiments, the second contact object isan email contact object. In some embodiments, the second contact objectis a telephone number object having a second telephone number differentfrom the return telephone number. In some embodiments, the secondcontact object is an instant messaging object. For example, in someembodiments, in response to a tap or other predefined gesture on icon2808 in the top row in UI 2800B (FIG. 12B), corresponding contactinformation is displayed in UI 2800C (FIG. 12C). In the example of FIG.12C, work telephone number 2816, from which the two missed calls weremade, corresponds to the first contact object. Any of objects 2818,2820, and 2822 could correspond to the second contact object.

Upon detecting user selection of the second contact object (5018), acommunication is initiated with the respective caller via a modalitycorresponding to the second contact object (5020). In some embodiments,in which the second contact object is an email contact object, themodality corresponding to the second contact object includes sending anemail message. In some embodiments, in which the second contact objectis a telephone number object having a second telephone number differentfrom the return telephone number, the modality corresponding to thesecond contact object includes initiating a telephone call to the secondtelephone number. In some embodiments, in which the second contactobject is an instant messaging object, the modality corresponding to thesecond contact object includes sending an instant message. In someembodiments, detecting contacts with either the first portion or secondportion of an item makes it easy for a user to either: (a) immediatelycall back the phone number associated with the missed call—withouthaving to view the contact information associated with the missed call(e.g., FIG. 12C), or (b) view the contact information to choose from aplurality of communication modalities associated with the missed caller.

While the missed telephone call handling process 5100 described aboveincludes a number of operations that appear to occur in a specificorder, it should be apparent that the process 5100 can include more orfewer operations, which can be executed serially or in parallel (e.g.,using parallel processors or a multi-threading environment), an order oftwo or more operations may be changed and/or two or more operations maybe combined into a single operation.

FIG. 25 is a flow diagram illustrating a process 5200 for handlingmissed telephone calls at a portable electronic device with a touchscreen display in accordance with some embodiments. Missed telephonecall information is displayed, including a list of items. At least oneof the items corresponds to a plurality of missed telephone calls from arespective caller (5202). In some embodiments, a respective item in thelist of items corresponds to a plurality of missed telephone calls froma plurality of distinct telephone numbers associated with the respectivecaller (5204). In some embodiments, at least two of the plurality ofmissed telephone calls from the respective caller comprise missedtelephone calls from at least two different telephone numbers associatedwith the respective caller (5208). In some embodiments, a respectiveitem in the list of items corresponds to one or more VoIP calls havingan associated IP address (5206). Displaying a single item in the list ofitems that corresponds to a plurality of missed telephone callscondenses the missed call list and makes it easy for a user to determinewhich people are trying to contact the user and how many times they havetried to contact the user.

In some embodiments, a scrolling gesture comprising substantiallyvertical movement of a user contact with the touch screen display isdetected (5010). In response, the displayed list of items is scrolled(5210). The scrolling gesture provides a simple way for the user torapidly scan the list of items.

Upon detecting user selection of an item in the list of items (5212),contact information is displayed for a respective caller correspondingto the user-selected item. The contact information includes a pluralityof contact objects (5214). In some embodiments, examples of contactobjects include the examples described above with regard to operation5016 in FIG. 23. Upon detecting user selection of a respective contactobject of the plurality of contact objects (5216), a communication isinitiated with the respective caller via a modality corresponding to theuser-selected contact object (5218). In some embodiments, examples ofmodalities include the examples described above with regard to operation5020 in FIG. 23. Providing a plurality of contact objects makes it easyfor a user to choose and initiate communications with the missed callerby any available communication modality, rather than being limited tocalling back the missed caller at the phone number associated with themissed call. For example, rather than calling Bruce Walker back at hiswork number, a user can just as easily call Bruce at home or send Brucean email message,

While the missed telephone call handling process 5200 described aboveincludes a number of operations that appear to occur in a specificorder, it should be apparent that the process 5200 can include more orfewer operations, which can be executed serially or in parallel (e.g.,using parallel processors or a multi-threading environment), an order oftwo or more operations may be changed and/or two or more operations maybe combined into a single operation. For example, operations 5010 and5012 may be omitted if the item to be selected in operation 5014 isdisplayed initially in operation 5002. In another example, alloperations except operation 5202 may be omitted.

FIG. 26 is a flow diagram illustrating a process 5300 for handlingtelephone call information at a portable electronic device with a touchscreen display with a plurality of user interface objects in accordancewith some embodiments. Telephone call information is displayed,including a list of items. At least one of the items corresponds to aplurality of telephone calls with a respective caller (5302). Forexample, UI 2800A (FIG. 12A) displays telephone call information for allrecent calls. The entry for Kim Brook 2802 corresponds to threetelephone calls, as indicated by number 2804. Displaying a single itemin the list of items that corresponds to a plurality of missed telephonecalls condenses the missed call list and makes it easy for a user todetermine which people are trying to contact the user and how many timesthey have tried to contact the user. A scrolling gesture comprisingsubstantially vertical movement of a user contact with the touch screendisplay is detected (5010). For example, vertical gesture 2814 isdetected. In response, the display of telephone call information isscrolled (5304). The scrolling gesture provides a simple way for theuser to rapidly scan the list of items.

While the prior telephone call handling process 5300 described aboveincludes a number of operations that appear to occur in a specificorder, it should be apparent that the process 5300 can include more orfewer operations, which can be executed serially or in parallel (e.g.,using parallel processors or a multi-threading environment), an order oftwo or more operations may be changed and/or two or more operations maybe combined into a single operation

FIG. 27 is a flow diagram illustrating a process 5400 for handling priortelephone calls at a portable electronic device with a touch screendisplay with a plurality of user interface objects in accordance withsome embodiments. A list of items for prior telephone calls is displayed(5402). In some embodiments, a single item in the list of itemscorresponds to a plurality of prior telephone calls (5404). For example,UI 2800A (FIG. 12A) displays telephone call information for all recentcalls. The entry for Kim Brook 2802 corresponds to three telephonecalls, as indicated by number 2804. Displaying a single item in the listof items that corresponds to a plurality of missed telephone callscondenses the missed call list and makes it easy for a user to determinewhich people are trying to contact the user and how many times they havetried to contact the user.

Upon detecting finger contact with a first portion of a user-selecteditem in the list (5406), a telephone call is initiated to a primarytelephone number associated with the user-selected item (5408). In someembodiments, for example, in response to a tap or other predefinedgesture on a row in UI 2800A (FIG. 12A) other than on icon 2808, areturn telephone call is initiated to the corresponding number for thatrow.

Upon detecting finger contact with a second portion of the respectiveitem in the list (5410) (e.g., icon 2808), contact information isdisplayed for a respective caller associated with the user-selected item(5412). The displayed contact information includes a plurality ofcontact objects that include a first contact object and a second contactobject. The first contact object comprises a telephone number objecthaving the primary telephone number. In some embodiments, the secondcontact object is an email contact object, an instant messaging object,or a telephone number object having a secondary telephone numberdifferent from the primary telephone number.

Upon detecting user selection of the second contact object (5414), acommunication is initiated with the respective caller via a modalitycorresponding to the second contact object (5416). In some embodiments,in which the second contact object is an email contact object, themodality corresponding to the second contact object includes sending anemail message. In some embodiments, in which the second contact objectis a telephone number object having a secondary telephone numberdifferent from the primary telephone number, the modality correspondingto the second contact object includes initiating a telephone call to thesecondary telephone number. In some embodiments, in which the secondcontact object is an instant messaging object, the modalitycorresponding to the second contact object includes sending an instantmessage. In some embodiments, examples of contact objects andcorresponding modalities correspond to the examples provided with regardto operations 5016 and 5020 in FIG. 23. In some embodiments, detectingcontacts with either the first portion or second portion of an itemmakes it easy for a user to either: (a) immediately call back the phonenumber associated with the missed call—without having to view thecontact information associated with the missed call (e.g., FIG. 12C), or(b) view the contact information to choose from a plurality ofcommunication modalities associated with the missed caller.

While the prior telephone call handling process 5400 described aboveincludes a number of operations that appear to occur in a specificorder, it should be apparent that the process 5400 can include more orfewer operations, which can be executed serially or in parallel (e.g.,using parallel processors or a multi-threading environment), an order oftwo or more operations may be changed and/or two or more operations maybe combined into a single operation.

FIG. 28 is a flow diagram illustrating a process 5500 for handlingincoming telephone calls at a portable electronic device with a touchscreen display with a plurality of user interface objects in accordancewith some embodiments. An incoming telephone call from a caller isdetected (5502). In some embodiments, contact information correspondingto the caller is identified (5504). A text identifier of the caller(e.g., the caller's name 3102, FIG. 15A) and an image associated withthe caller (e.g., graphic 3104) are displayed (5506). In someembodiments, the text identifier and the image are from the identifiedcontact information. A call answer icon (e.g., icon 3108, FIG. 15A) isdisplayed, which if selected by a user of the device, answers theincoming telephone call. A call decline icon (e.g., icon 3106) isdisplayed, which if selected by the user of the device, declines theincoming call. This process 5500 provides call information and explainsthe call options available to a user in a simple, clear manner.

While the incoming telephone call handling process 5500 described aboveincludes a number of operations that appear to occur in a specificorder, it should be apparent that the process 5500 can include more orfewer operations, which can be executed serially or in parallel (e.g.,using parallel processors or a multi-threading environment), an order oftwo or more operations may be changed and/or two or more operations maybe combined into a single operation.

FIG. 29 is a flow diagram illustrating a process 5600 for handlingestablished telephone calls at a portable electronic device with a touchscreen display with a plurality of user interface objects in accordancewith some embodiments. Upon detecting that a telephone call between auser of the device and another entity has been established (5602), thefollowing items are displayed (5604): a mute icon for muting amicrophone of the device; a keypad icon for displaying a keypad; aspeaker icon for activating a speaker mode of the device; a conferencecall icon or add call icon for forming a multi-party telephone callbetween the user, the other entity and at least one additional entity; acall hold icon for suspending the telephone call; a contacts icon fordisplaying a contacts list; and an end call icon for ending thetelephone call. Examples of these items are illustrated in UI 3000B,FIG. 14B, and UI 3000D, FIG. 14D. In some embodiments, not all of thelisted items are displayed. For example, in UI 3000B (FIG. 14B), thecontacts icon and the keypad icon are not displayed. This process 5600provides call information and explains the call options available to auser in a simple, clear manner.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

1. A graphical user interface on a portable electronic device with atouch screen display, a memory, and one or more processors to executeone or more programs stored in the memory, the graphical user interfacecomprising: a list of items, the list comprising a plurality ofinteractive displayed items associated with telephone calls, wherein: atleast one interactive displayed item in the list is associated with aprior telephone call and is also associated with contact informationstored in the portable electronic device; each such interactivedisplayed item associated with both a prior telephone call and contactinformation comprises at least a first interactive displayed portion anda second interactive displayed portion, the second interactive displayedportion being distinct from the first interactive displayed portion; afinger tap input is detected at a first user selected interactivedisplayed item associated with both a prior telephone call and contactinformation, wherein the finger tap input is detected at the firstinteractive displayed portion of the first user selected interactivedisplayed item, and in response to that input a telephone call isinitiated to a telephone number associated with the first user selectedinteractive displayed item; a finger tap input is detected at a seconduser selected interactive displayed item associated with both a priortelephone call and contact information, wherein the finger tap input isdetected at the second interactive displayed portion of the second userselected interactive displayed item, and in response to that inputcontact information is displayed for a caller corresponding to thesecond user selected interactive displayed item, the displayed contactinformation including simultaneous display of a plurality of contactobjects, the plurality of contact objects comprising: a first contactobject associated with a telephonic communication modality for callingthe caller, and a second contact object associated with a non-telephoniccommunication modality for contacting the caller; and in response todetecting user selection of the second contact object, a communicationis initiated with the corresponding caller through the non-telephoniccommunication modality corresponding to the second contact object. 2.The graphical user interface of claim 1, wherein the second contactobject is an email contact object, and wherein initiating thecommunication with the corresponding caller through the non-telephoniccommunication modality corresponding to the second contact objectincludes preparing an email message with an email address associatedwith the second contact object, ready for text input by the user.
 3. Thegraphical user interface of claim 1, wherein the second contact objectis an instant messaging object, and wherein initiating the communicationwith the corresponding caller through the non-telephonic communicationmodality corresponding to the second contact object includes preparingan instant message to a number associated with the second contactobject, ready for text input by the user.
 4. The graphical userinterface of claim 1, wherein a single item in the list of itemscorresponds to a plurality of consecutive missed telephone calls.
 5. Thegraphical user interface of claim 1, wherein, while the list of itemscomprising prior telephone calls is displayed, a number indicating aplurality of consecutive missed telephone calls is displayed within arespective single item in the list.
 6. The graphical user interface ofclaim 1, wherein a single item in the list of items corresponds to aplurality of missed telephone calls from a plurality of distincttelephone numbers associated with a respective caller.
 7. The graphicaluser interface of claim 1, wherein the second interactive displayedportion of the second user selected interactive displayed item isidentified by an icon displayed within the second user selectedinteractive displayed item.
 8. The graphical user interface of claim 1,wherein the second contact object is a contact object associated withsending an email to the caller and the plurality of simultaneouslydisplayed contact objects includes a third contact object associatedwith sending an instant message to the caller.